-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Week 2: Difficulty Spike #5
Conversation
Just created a week 2 journal entry to set it up
Created a halfway decent outline
Solid outline! 👍 |
Probably a good summation of what everyone else is feeling. Why no love for the MVC? Though, JavaScript doesn't care about your wedding. 👍 |
Added lots and lots of stuff, committing to keep it saved
Added a lot more stuff
Displays nothing, renders the page as though the element doesn't exist, used by javascript | ||
|
||
1. script: defaults to none | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like how you broke out the property values into their own sections. Maybe use backticks and links to the reference documentation for quick finds later. Also, remember to put a space after your hash marks.
Added topics to parking lot
Made final draft
Took me a while to find your change even with split diff view. Sneaky. I approve. Can't improve on perfection can we? 👍 |
|
||
Right off the bat I had great difficulty figuring out how to make the javascript affect elements of the HTML and CSS. Even getting one piece of the code to work and just making it log a tracer bullet for clicking certain things was a big pain in the ass, and then we had plenty more to do. Eventually as we progressed, I could get the elements already on the page to work but still not be able to dynamically add things. But God comes through and eventually everything clicked when I realized that in order to get added tasks to work right the event listeners would need to be called at their adding. This was also when I realized that the initial code that added the event listeners stopped at the loading of the page and never ran again. lodash _.forEach would not cut it, so I wrapped each of my event listener adding chunks of code in functions and called them EVERY TIME I ADDED A TASK. It worked beautifully. If only I had figured this out earlier during the weekend I could have possibly accomplished a little more, but I was satisfied to have gotten it working to a fairly functional point. | ||
|
||
How do I feel? Exhausted, this coding stuff is a major brain fryer. I find however, that as I let the material kind of simmer in my brain after being wrecked by it in class, it slowly integrates into my knowledge base, and it's a great feeling. I'm actually enjoying myself when I'm able to devote most of my time to coding and making it work, and if I didn't have a fiancee living at home with me driving me up the wall about this wedding I could be a hermit who codes for 12 hours a day. We did get our engagement photos taken on Sunday, over three hours that could have been devoted to making the todo application edit tasks, but it was nice regardless. Overall I would say I'm happy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 7: last sentence - I would add a comma after "Overall"
Added code into my final draft, put Phillip's grammar correction in
Added a bunch about fonts, lines, and text
corrected line
Good job on your journal entry Michael! 👍 Great to see the way you tackle every code difficulty you come across. Keep up the good work 😃 |
Great job! I like that you included your own code in your journal. That is a fantastic idea! 👍 |
Added data attributes
Just created a week 2 journal entry to set it up